Project reviewer-safe workflow results - #1815
Merged
Merged
Conversation
This was referenced Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stage an explicit, bounded reviewer-safe projection of the native agent workflow result instead of uploading the complete runtime envelope. Public control, verification, publication, output projection, access, failure, artifact declaration, and canonical transcript provenance fields remain available, while raw runtime/provider/model/tool payloads are excluded.
What changed
agent-task-workflow-result.jsonfiles.runtime_result,outputs.engine_data, verification stream bodies, raw diagnostics, and undeclared top-level payloads from the review artifact.runtime_resultandoutputs.engine_data.How to test
git fetch origin pull/1815/head:review-1815, and rungit switch review-1815.npm ci; expect dependency installation and the workspace TypeScript build to complete successfully.TMPDIR=/tmp npm run test:runtime-sources-materialization; expectruntime sources materialization ok. This exercises the PHP-shaped nested-payload regression and existing disguised-source artifact rejection.TMPDIR=/tmp npm run test:agent-task-contracts; expect the agent-task contracts, canonical evidence, workflow interface, runtime materialization, and reusable workflow suites to pass.npm run build; expect TypeScript compilation and CLI executable validation to complete without errors.Backwards compatibility
The internal
.codebox/agent-task-workflow-result.jsonproduced during execution is unchanged, as are reusable-workflow outputs. Only the uploaded reviewer copy becomes intentionally narrower. Existing public control/publication fields and canonical transcript provenance remain; consumers that incorrectly depended on raw runtime/provider/model/tool data inside the uploaded artifact must use the canonical sanitized transcript or declared public projections instead.Evidence
runtime_resultplus the equivalentoutputs.engine_dataexposure.prepare-agent-task-upload.mjs; source-content rejection remains active for declared artifacts and every other staged file, so the behavior is no broader than the hosted evidence.AI assistance
Source relationships